Skip to content

Fix use of private wrap-fx in macro#160

Merged
lilactown merged 2 commits intolilactown:masterfrom
SevereOverfl0w:wrap-fx
Jan 5, 2026
Merged

Fix use of private wrap-fx in macro#160
lilactown merged 2 commits intolilactown:masterfrom
SevereOverfl0w:wrap-fx

Conversation

@SevereOverfl0w
Copy link
Contributor

This ends up expanding in the caller's namespace, which references the private wrap-fx and leads to a compiler warning under Figwheel. I believe Shadow is suppressing these so it wasn't caught.

This ends up expanding in the caller's namespace, which references the
private `wrap-fx` and leads to a compiler warning under Figwheel.  I
believe Shadow is suppressing these so it wasn't caught.
Copy link
Owner

@lilactown lilactown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, bummer about the difference between shadow and other compilers. Change makes sense!

@lilactown lilactown merged commit 6b3d4d3 into lilactown:master Jan 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants